Blog: Running DDEV in CI with WarpBuild #515
Conversation
| pubDate: 2026-01-01 | ||
| modifiedDate: 2026-01-03 |
There was a problem hiding this comment.
These need bumping before publishing.
deviantintegral
force-pushed
the
warpbuild-post
branch
from
da5cb30 to
8c0982d
Compare
|
🌐 Fork Preview for PR #515 https://pr-515.ddev-com-fork-previews.pages.dev This preview updates automatically when you push changes to your fork. |
|
Looking forward to trying it out, thanks! |
rfay
left a comment
rfay
left a comment
There was a problem hiding this comment.
Thanks for the great work on this! Made a few suggestions, will also ask Copilot to take a pass.
There was a problem hiding this comment.
Pull request overview
This PR adds a blog post documenting how Lullabot uses WarpBuild to significantly improve DDEV startup performance in CI environments, specifically for GitHub Actions workflows. The post shares practical implementation details and performance results from using WarpBuild's Snapshot feature to cache DDEV environments.
Changes:
- New blog post describing WarpBuild integration with DDEV for CI performance optimization
- New author profile for Andrew Berry
- Minor cleanup removing unused "Resources" category from README documentation
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| src/content/blog/ddev-ci-warpbuild.md | Technical blog post explaining WarpBuild setup, configuration, and performance results for DDEV in CI |
| src/content/authors/andrew-berry.md | Author profile for the blog post author |
| README.md | Removes unused "Resources" category from blog category list |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Randy Fay <randy@randyfay.com>
Co-authored-by: Randy Fay <randy@randyfay.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
deviantintegral
force-pushed
the
warpbuild-post
branch
from
ece99fb to
0054be9
Compare
|
Rewrite is done! The example now is broken into separate sections, but they should all combine into a single file without any references to actions in other directories. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated 4 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
@rfay prettier is failing on the yaml blocks, but the indentation matters. Remove the indentation (and make this less copy-paste-able) or change something in prettier? |
|
Shouldn't be hard, we have yaml blocks lots of places. What does |
|
I updated it to make |
stasadev
left a comment
stasadev
left a comment
There was a problem hiding this comment.
Looks good to me!
Great technique, it should have been available in GitHub Actions by default.
I recently noticed https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images which might solve this but in a different way. I don't like that everything is controlled via the UI, at the org level and not the repo level. I expect WarpBuild will still be cheaper. But I haven't actually tried it yet! |
rfay
left a comment
rfay
left a comment
There was a problem hiding this comment.
Thanks, it's great! Minor suggestion for rewording the second sentence, you can do it any way you like.
If you have any more tolerance for it, there are two things that would make this really, really useful:
- A simple github repo that demonstrates it in context
- A diagram explaining what in the world is going on with all the moving parts.
I am not assuming you have any more tolerance, and I don't want to put a roadblock in front of you.
Thanks!
| - Performance | ||
| --- | ||
|
|
||
| For most developers, DDEV solves a common challenge: making sure that each developer has a consistent, stable local environment for building their web application. At Lullabot, as we had more and more success with DDEV, but another related issue kept coming up: how do we grow and develop our use of continuous integration and automated testing while avoiding the same challenges DDEV solved for us? |
There was a problem hiding this comment.
The sentence isn't quite right as is. I'm sure it could be done more ways. Here's one. But the second sentence of the opening should be grammatically correct.
| For most developers, DDEV solves a common challenge: making sure that each developer has a consistent, stable local environment for building their web application. At Lullabot, as we had more and more success with DDEV, but another related issue kept coming up: how do we grow and develop our use of continuous integration and automated testing while avoiding the same challenges DDEV solved for us? | |
| For most developers, DDEV solves a common challenge: making sure that each developer has a consistent, stable local environment for building their web application. We had more and more success with DDEV at Lullabot, but another related issue kept coming up: how do we grow and develop our use of continuous integration and automated testing while avoiding the same challenges DDEV solved for us? |
|
This made me wonder whether we can significantly improve our huge DDEV tests with the large images approach we probably get with our nonprofit teams plan, or with WarpBuild itself if they have a nonprofit plan. |
3 participants
The Issue
I'm following up from the suggestion at ddev/ddev#7054 (comment).
How This PR Solves The Issue
It documents what we've done to effectively use DDEV in GitHub Actions.
Review at https://pr-515.ddev-com-fork-previews.pages.dev/blog/ddev-ci-warpbuild/